Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #344 #348

Merged
merged 1 commit into from
Mar 30, 2016
Merged

Fixes #344 #348

merged 1 commit into from
Mar 30, 2016

Conversation

Laura-O
Copy link
Member

@Laura-O Laura-O commented Mar 22, 2016

See #344 for a longer explanation.

These changes clarify that E2e can also be relevant when there is no proof that a competitor used the scramble sequence to derive his solution intentionally.
With the new Fewest Moves scramble sequences implemented in TNoodle, starting a solution with the inverse of more than the last 4 moves of the scramble is a good evidence that the solution was derived from the scramble as the first and the last three moves of the scramble sequence are pointless. However, this is still a "should", so in the rare case that beginning a solution with these moves is reasonable, this is not necessarily a DNF.

Question
Is "solutions beginning with more than 4 moves of the inverse scramble sequence" clear?
It can be interpreted that solutions should not begin with any 4 moves of the inverse scramble. But I have no idea how to clarify that here.

@viroulep
Copy link
Member

I like how the final changes look.

Purely technical comment : the commits history is starting to get a bit messy for a "small" resulting diff, would you mind squashing your 6 commits into one, and git push --force it to fixes-FMC ?

PS: PRs are exactly the places where you want to ignore the note at the end of the linked article :p

Examples for DNFs in Fewest Moves

scrambling -> scramble

Clarified E2e again

Added clarifiction

scrambling algorithm -> scramble sequence
@Laura-O
Copy link
Member Author

Laura-O commented Mar 24, 2016

Good idea! :-)

@Claster
Copy link
Contributor

Claster commented Mar 24, 2016

Looks good to me.
I like how it says "example of solutions that SHOULD result in a DNF". That is, if there is a very obvious block that uses 4 moves from scramble, it could be kept, at the discretion of a delegate. I just hope that competitors and delegates won't interpret this word "should" as "must".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants